OpenEdge Getting Started:<br />WebSpeed Essentials Configuring a WebSpeed Transaction Server

The WebSpeed Transaction Server consists of the processes that handle the server-side activity of your WebSpeed applications. Use the following procedure to configure the WebSpeed Transaction Server and NameServer for developing and deploying WebSpeed applications in Windows.

Make sure the AdminService is running. If the AdminService is not running, you must start it. (For information on starting it, see the "AdminService" section.)

Start an existing NameServer or create a new NameServer instance. You can create and start a NameServer by using the Progress Explorer; or you can edit the ubroker.properties file to create an instance and then use the NSMAN utility to start the instance. When you configure a NameServer instance, you can set it to start up by default whenever the AdminService starts.

Note: The NameServer can be on any machine in your network, even a UNIX machine. You can configure a WebSpeed environment without a NameServer. For more information, see the "“No NameServer” configurations" section.

If you are using the Progress Explorer, see the online help for information about creating and starting an instance. If you are editing the ubroker.properties file, see the "Editing the ubroker.properties file" section.

To start a local instance of the NameServer from the command line, use the following command:


nsman -name NS1 -start

Where NS1 is the name of the NameServer.

To start a remote instance of the NameServer from the command line, use the following command:


nsman -name NS1 -host `host-name` -port `port` -user `user-name` -start

Where host-name is the name of the host machine on which you want the instance to run, port is the port number on the AdminService, and user-name is the user ID of the system account that started the AdminServer.

Start an existing WebSpeed Transaction Server or create a new Transaction Server instance. You can create and start a Transaction Server by using the Progress Explorer; or you can edit the ubroker.properties file to create an instance and then use the WTBMAN utility to start the instance. When you configure a Transaction Server instance, you can set it to start up by default whenever the AdminService starts.

See the Progress Explorer online help for information about creating and starting an instance.

To start a local instance of the WebSpeed Transaction Server from the command line, use the following command:


wtbman -name wsbroker1 -start

Note: The WebSpeed Transaction Server consists of a broker and agents. The default WebSpeed broker is wsbroker1. When you start the broker, the agents are also started.

To start a remote instance of the WebSpeed Transaction Server from the command line, use the following command:


wtbman -name `broker` -host `host` -port `port` -user `user` -start

Where broker is the name of the WebSpeed broker, host is the name of the host machine on which you want the instance to run, port is the port number on the AdminService, and user is the user ID of the system account under which the Transaction Server will run. If you specify a host name, the Explorer prompts you for a user name (if you do not supply it) and password.

By using either the Progress Explorer or the command-line utilities, you can also stop a NameServer or WebSpeed Transaction Server instance, check its status, and increase or reduce the number of running WebSpeed agents. For more information, see the Progress Explorer online help and the "Progress Explorer" section, and the "Managing the WebSpeed Transaction Server" section.